| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-RI.1.3.2.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-RI.1.3.2 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | RI_1_3_2_Manage_Record_Entry_Amended__Corrected_and_Augmented_State |
| Title | RI.1.3.2 Manage Record Entry Amended, Corrected and Augmented State (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Manage Record Entries amended, corrected or augmented after finalization (or signature/attestation). |
| Purpose | Clinicians need the ability to correct, amend or augment Record Entries once they have been completed. When an amendment, correction or augmentation has been made, principles for documentation practices require that the original documentation must be accessible, readable, and unobliterated. A user must have a clear indication that modifications have been made to an Record Entry. There is optionality in how a system may identify a Record Entry that has been corrected or amended – a flag or indicator could be displayed, the text could be in a different font, etc. The original Record Entry is not required to be displayed, but can be linked or traced back. The original Record Entry and each successive amendment, correction or augmentation should be retained for the legally prescribed timeframe as defined by scope of practice, organizational policy, and/or jurisdictional law. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Manage Record Entries amended, corrected or augmented after finalization (or signature/attestation).
Clinicians need the ability to correct, amend or augment Record Entries once they have been completed. When an amendment, correction or augmentation has been made, principles for documentation practices require that the original documentation must be accessible, readable, and unobliterated. A user must have a clear indication that modifications have been made to an Record Entry. There is optionality in how a system may identify a Record Entry that has been corrected or amended – a flag or indicator could be displayed, the text could be in a different font, etc. The original Record Entry is not required to be displayed, but can be linked or traced back. The original Record Entry and each successive amendment, correction or augmentation should be retained for the legally prescribed timeframe as defined by scope of practice, organizational policy, and/or jurisdictional law.
| RI.1.3.2#01 | SHALL |
The system SHALL provide the ability to update a Record Entry for purposes of amendment, correction or augmentation, conforming to function [[RI.1.1.2]] (Amend Record Entry Content). |
| RI.1.3.2#02 | SHALL |
The system SHALL provide the ability to tag a Record Entry as an amendment, a correction of erroneous information and the reason, or an augmentation to supplement content. |
| RI.1.3.2#03 | SHALL |
The system SHALL capture, maintain and render the corresponding date, time, and user specifying when and by whom a Record Entry was amended, corrected, or augmented, conforming to function [[RI.1.1.2.1]] (Evidence of Record Entry Amendment Event). |
| RI.1.3.2#04 | SHALL |
The system SHALL present the current version and provide a link or clear direction for accessing previous version(s) of the Record Entry. |
| RI.1.3.2#05 | SHALL |
The system SHALL manage all versions of the Record Entry for the legal retention period, conforming to function [[RI.1.2.1]] (Manage Record Entries). |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-RI.1.3.2",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Manage Record Entries amended, corrected or augmented after finalization (or signature/attestation).</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Clinicians need the ability to correct, amend or augment Record Entries once they have been completed. When an amendment, correction or augmentation has been made, principles for documentation practices require that the original documentation must be accessible, readable, and unobliterated. A user must have a clear indication that modifications have been made to an Record Entry. There is optionality in how a system may identify a Record Entry that has been corrected or amended – a flag or indicator could be displayed, the text could be in a different font, etc. The original Record Entry is not required to be displayed, but can be linked or traced back. The original Record Entry and each successive amendment, correction or augmentation should be retained for the legally prescribed timeframe as defined by scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.3.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to update a Record Entry for purposes of amendment, correction or augmentation, conforming to function [[RI.1.1.2]] (Amend Record Entry Content).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.3.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to tag a Record Entry as an amendment, a correction of erroneous information and the reason, or an augmentation to supplement content.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.3.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL capture, maintain and render the corresponding date, time, and user specifying when and by whom a Record Entry was amended, corrected, or augmented, conforming to function [[RI.1.1.2.1]] (Evidence of Record Entry Amendment Event).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.3.2#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL present the current version and provide a link or clear direction for accessing previous version(s) of the Record Entry.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>RI.1.3.2#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL manage all versions of the Record Entry for the legal retention period, conforming to function [[RI.1.2.1]] (Manage Record Entries).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-RI.1.3.2",
"version" : "2.1.0",
"name" : "RI_1_3_2_Manage_Record_Entry_Amended__Corrected_and_Augmented_State",
"title" : "RI.1.3.2 Manage Record Entry Amended, Corrected and Augmented State (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Manage Record Entries amended, corrected or augmented after finalization (or signature/attestation).",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Clinicians need the ability to correct, amend or augment Record Entries once they have been completed. When an amendment, correction or augmentation has been made, principles for documentation practices require that the original documentation must be accessible, readable, and unobliterated. A user must have a clear indication that modifications have been made to an Record Entry. There is optionality in how a system may identify a Record Entry that has been corrected or amended – a flag or indicator could be displayed, the text could be in a different font, etc. The original Record Entry is not required to be displayed, but can be linked or traced back. The original Record Entry and each successive amendment, correction or augmentation should be retained for the legally prescribed timeframe as defined by scope of practice, organizational policy, and/or jurisdictional law.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-RI.1.3.2-01",
"label" : "RI.1.3.2#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to update a Record Entry for purposes of amendment, correction or augmentation, conforming to function [[RI.1.1.2]] (Amend Record Entry Content)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-RI.1.3.2-02",
"label" : "RI.1.3.2#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to tag a Record Entry as an amendment, a correction of erroneous information and the reason, or an augmentation to supplement content."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-RI.1.3.2-03",
"label" : "RI.1.3.2#03",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL capture, maintain and render the corresponding date, time, and user specifying when and by whom a Record Entry was amended, corrected, or augmented, conforming to function [[RI.1.1.2.1]] (Evidence of Record Entry Amendment Event)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-RI.1.3.2-04",
"label" : "RI.1.3.2#04",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL present the current version and provide a link or clear direction for accessing previous version(s) of the Record Entry."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-RI.1.3.2-05",
"label" : "RI.1.3.2#05",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL manage all versions of the Record Entry for the legal retention period, conforming to function [[RI.1.2.1]] (Manage Record Entries)."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.